In the non-cudf API, we have:

  module Diagnostics : sig
    include module type of Zeroinstall_solver.Diagnostics(Solver.Output)
  end

  val diagnostics_rolemap : diagnostics -> Diagnostics.t

Is there a reason to do it differently for cudf?

the current interface does not export Solver but in any case this PR cleans up the data that are not going to be used (e.g. Context.t in role, some useless ints and cases such as ClassConflict, MissingCommand, …

In any case, in my opinion, exporting it this way makes it much cleaner and avoids back and forth between the definitions to actually understand how to use the data.

OK. The asserts look safe to me, given the cudf stuff doesn't use machine groups, class conflicts or commands.

Moved to ocaml-opam/opam-0install-cudf#1